Skip Headers

Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# Troubleshooting RMAN TRANSPORT TABLESPACE

When the RMAN `TRANSPORT` `TABLESPACE` command fails, the failed auxiliary instance files are left intact in the auxiliary instance destination for troubleshooting.

Common causes for problems during `TRANSPORT` `TABLESPACE` include the following:

- Troubleshooting RMAN TRANSPORT TABLESPACE: Insufficient Shared Pool

- Troubleshooting RMAN TRANSPORT TABLESPACE: Filename Conflicts

## Troubleshooting RMAN TRANSPORT TABLESPACE: Insufficient Shared Pool

If you see an error related to shared pool size, create an auxiliary instance parameter file with a larger value for `SHARED_POOL_SIZE`, as described in "Customize Shared Pool Size in RMAN TRANSPORT TABLESPACE" .

## Troubleshooting RMAN TRANSPORT TABLESPACE: Filename Conflicts

If your `SET NEWNAME`, `CONFIGURE AUXNAME` and `DB_FILE_NAME_CONVERT` cause multiple files in the auxiliary or recovery sets to have the same name, RMAN will report an error during the `TRANSPORT` `TABLESPACE` command. To correct the problem, use different values for these parameters to ensure that duplicate file names are not created.